core: refactor StateProcessor to accept ChainContext interface #32739
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lightclient
reviewed
Sep 25, 2025
fjl
reviewed
Sep 25, 2025
s1na
reviewed
Sep 26, 2025
s1na
reviewed
Sep 29, 2025
s1na
approved these changes
Sep 30, 2025
rjl493456442
approved these changes
Sep 30, 2025
rjl493456442
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pr implements #32733 to enable StateProcessor to be accepted custom data format.
Release notes
This introduces a breaking change to users using geth EVM as a library. The
NewStateProcessorfunction now takes one parameter which has the chainConfig embedded instead of 2 parameters.